Good question! My rationale here was that fastapi-cli is an end-user CLI, so I don't really see many realistic scenarios where a bump would cause issues. Even if a user had a super locked-down environment where they've pinned a specific version, they'd still need to update something to get the new CLI version anyway.

From a UX perspective, I'd also argue that suggestions on typos are commonplace in modern CLIs, so it'd be nice if we could ensure a consistent UX for all users. It'd be weird to have the CLI only provide suggestions if the user's deps happened to transitively resolve to 0.20.0, right? By bumping the lower bound, we guarantee everyone gets the same base experience.

I see where you're coming from, I'm just unsure whether we need to make that decision for users or not. They might have a pin on Typer in the same env for some other reason. Anyway I don't care strongly either way, just thought it was worth discussing. Will let Tiangolo make the final decision 😉

Thank you!

Commenting here just to reflect the internal discussion. 😅

Let's not bump here, most users will get the upgraded version, but if one of them has an app that has an upper bound pin, if we require this lowerbound, the package manager will just install an older version of fastapi-cli that doesn't have the lower bound pin, so better to keep this for now open, that way they can always get the latest version of fastapi-cli even if they have a lower bound pin for Typer for some other reason.

...at some point, we might end up adding a feature in Typer that we need here and we'll end up having the new lower bound pin anyway, but if we can skip it for now, let's do that. 🤓